Systems and methods for automated invoice entry

ABSTRACT

The present invention is directed to methods and systems for the transfer of bulk paper invoices into electronic invoices for electronic submission from a seller to a buyer. The systems and methods described herein use matching logic to transfer details of the paper invoices into electronic invoices, thereby streamlining the process of bulk invoicing.

BACKGROUND OF THE INVENTION

Traditional paper invoicing procedures typically involve the sellersending an invoice to a buyer which lists the purchases that have beenmade, and the buyer in turn sending the seller payment based on thetotal amount reflected in the invoice.

In order to avoid the hassle of lost invoices, payment, and to reducethe amount of wasted paper, electronic invoices are becoming morecommon. Invoices are sent electronically directly to the buyer and thebuyer can then remit payment either directly to the seller or throughthe buyer's bank.

However, there are still drawbacks to conventional electronic invoices.Bulk invoicing, for example, can be particularly time consuming, as eachindividual invoice must be uploaded into a computer before they are sentto the buyer in bulk. In addition, electronic invoicing often requiresmanual entry of information by the seller, which can result in losttime, and ultimately, lost money.

There remains a need to streamline the electronic invoicing process inorder to increase efficiency and accuracy, saving time and money forboth the buyer and the seller.

SUMMARY OF THE INVENTION

The present invention addresses the need in the art by providingefficient invoicing systems and methods for electronic invoicing.

In certain embodiments, the present invention is directed to acomputer-implemented method for generating an electronic invoicecomprising: receiving a set of invoice field values provided by a user;automatically mapping the invoice field values provided by the user tocreate mapped data; receiving an image of an invoice of the user; andapplying the mapped data fields to the image of the invoice to create anelectronic invoice.

In certain embodiment, the present invention is directed to a system forgenerating an electronic invoice comprising: a processor; a memory; andan application stored in the memory of the system and executable by theprocessor, wherein the application functions to: receive a set ofinvoice field values provided by a user; automatically map the invoicefield values provided by the user to create mapped data fields; receivean image of an invoice of the user; and apply the mapped data fields tothe image of the invoice to create an electronic invoice.

In certain embodiments, the present invention is directed to acomputer-readable storage medium storing computer code for implementinga method for generating an electronic invoice, wherein the computer codecomprises: code for receiving a set of invoice field values provided bya user; code for automatically mapping the invoice field values providedby the user to Create mapped data fields; code for receiving an image ofan invoice of the user; and code for applying the mapped data fields tothe image of the invoice to an electronic invoice.

In other embodiments, the present invention is directed to acomputer-implemented method for generating batch invoices comprising:receiving a set of invoice field values provided by a user;automatically mapping the invoice field values provided by the user tocreate mapped data fields; receiving a batch of production invoicescomprising individual production invoices of the user; and applying themapped data fields to the batch of production invoices to create a batchof electronic invoices.

In other embodiments, the present invention is directed to a system forgenerating batch invoices comprising: a processor; a memory; and anapplication stored in the memory of the system and executable by theprocessor, wherein the application functions to: receive a set ofinvoice field values provided by a user; automatically map the invoicefield values provided by the user to create mapped data fields; receivea batch of production invoices comprising individual production invoicesfrom the user; and apply the mapped data fields to the batch ofproduction invoices to create a batch of electronic invoices

In other embodiments, the present invention is directed to acomputer-readable storage medium storing computer code for implementinga method for generating batch invoices, wherein the computer codecomprises: code for receiving a set of invoice field values provided bya user; code for automatically mapping the invoice field values providedby the user to create mapped data fields; code for receiving a batch ofproduction invoices comprising individual production invoices from theuser; and code for applying the mapped data fields to the batch ofproduction invoices to create a batch of electronic invoices.

In yet other embodiments, the present invention is directed to acomputer-implemented method for invoice exchange comprising: providing anetwork membership to a buyer-member and seller-members; providingnon-network access information to the buyer-member for use with anon-member seller; providing an interface to the non-member seller;receiving the non-network access information from the non-member seller;receiving invoice information for a transaction with the firstbuyer-member from the non-member seller to create a completed invoice;validating the non-network access information; and providing thecompleted invoice to the buyer-member

In yet other embodiments, the present invention is directed to a systemfor invoice exchange comprising: a processor; a memory; and anapplication stored in the memory of the system and executable by theprocessor, wherein the application functions to: provide a networkmembership to a buyer-member and seller-members; provide non-networkaccess information to the buyer-member for use with a non-member seller;provide an interface to the non-member seller; receive the non-networkaccess information from the non-member seller; receive invoiceinformation for a transaction with the first buyer-member from thenon-member seller to create a completed invoice; validate thenon-network access information; and provide the completed invoice to thebuyer-member.

In yet other embodiment, the present invention is directed to acomputer-readable storage medium storing computer code for invoiceexchange, wherein the computer code comprises: code for providing anetwork membership to a buyer-member and seller-members; code forproviding non-network access information to the buyer-member for usewith a non-member seller; code for providing an interface to thenon-member seller; code for receiving the non-network access informationfrom the non-member seller; code for receiving invoice information for atransaction with the first buyer-member from the non-member seller tocreate a completed invoice; code for validating the non-network accessinformation; and code for providing the completed invoice to thebuyer-member.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts a flow chart for preparing a test invoice using thesystem, according to certain embodiments of the present invention.

FIG. 2 depicts a flow chart for entering invoices into the system,according to an embodiment of the present invention.

FIG. 3 a depicts a flow chart of the entry process of invoices,according to an embodiment of the present invention.

FIG. 3 b depicts a flow chart of the rejection process for invoices,according to an embodiment of the present invention.

FIG. 4 depicts a flow chart of the process for non-member seller invoiceentry into the system.

DETAILED DESCRIPTION

The invoicing systems and methods of the present invention automate theexchange of invoices by integrating buyers and sellers via a securesettlement network, allowing companies to optimize working capital,thereby turning accounts payable processing into a profit center. Theinvoicing system enhances the user's control over the end-to-endprocure-to-pay process. This on-demand technology platform allowscompanies to achieve effective payables automation, lowering costs andstreamlining processes by speeding the migration away from paper andmanual processes, reducing data entry and exception management andcapturing discounts related to payables spent. Through seamlessintegration with existing enterprise resource planning and legacyapplications, the capability of the invoicing system of the presentinvention supports invoice tracking and management through an onlineportal, directly connecting buyers and sellers. Benefits of this aspectof the present invention include, for example, reduced operational costsassociated with paper invoice processing, scanning and data entry,increased visibility and control over invoice tracking and history forbuyers and sellers, reduced seller inquiry calls by providing allday/all night access to information to sellers, communication of invoicestatus to all sellers for all invoices, including those submittedthrough the seller portal, originating from paper, e-file or electronicdata interchange (EDI), accommodation of sellers in every industrysegment with a suitable invoice options, from paper invoice processingto seller portal access to directed system integration, confirmation tolarge-seller integration and automated billing requirements, andtranslation of all invoice data types, including EDI, CVS, XML, AS2 orother electronic documents to buyer-specified formats. Further, as thesystem is preferably provided by an outside party, responsibility andcost of maintaining the system by the user is removed.

To access the benefits of the system of the present invention, bothbuyers and sellers enroll as members of the invoicing system whichallows them access to the system capabilities. In preferred embodiments,the system not only provides invoicing capabilities, but also automatespurchase orders, payments and discounts as well. The system of thepresent invention allows buyers to expand the maximum number of sellersthat receive electronic purchase orders and invoices, therefore alsoeliminating fax, postage, filing, storage and document administrationexpenses.

General System Requirements

Various embodiments of the system of the invention and variousadvantages are described above. The system of the invention or portionsof the system of the invention may be in the form of a “processingmachine,” i.e. a tangibly embodied machine, such as a general purposecomputer or a special purpose computer, for example. As used herein, theterm “processing machine” is to be understood to include at least oneprocessor that uses at least one memory. The memory stores a set ofinstructions. The instructions may be either permanently or temporarilystored in the memory or memories of the processing machine. Theprocessor executes the instructions that are stored in the memory ormemories in order to process data. The set of instructions may includevarious instructions that perform a particular task or tasks, such asany of the processing as described herein. Such a set of instructionsfor performing a particular task may be characterized as a program,software program, or simply software.

As noted above, the processing machine, which may be constituted, forexample, by the particular system and/or systems described above,executes the instructions that are stored in the memory or memories toprocess data. This processing of data may be in response to commands bya user or users of the processing machine, in response to previousprocessing, in response to a request by another processing machineand/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general purpose computer. However, the processing machinedescribed above may also utilize (or be in the form of) any of a widevariety of other technologies including a special purpose computer, acomputer system including a microcomputer, mini-computer or mainframefor example, a programmed microprocessor, a micro-controller, aperipheral integrated circuit element, a CSIC (Consumer SpecificIntegrated Circuit) or ASIC (Application Specific Integrated Circuit) orother integrated circuit, a logic circuit, a digital signal processor, aprogrammable logic device such as a FPGA, PLD, PLA or PAL, or any otherdevice or arrangement of devices that is capable of implementing thesteps of the processes of the invention.

The processing machine used to implement the invention may utilize asuitable operating system. Thus, embodiments of the invention mayinclude a processing machine running the Microsoft Windows® 7 operatingsystem, Microsoft Windows® Vista® operating system, the MicrosoftWindow®XP® operating system, the Microsoft Windows® NT® operatingsystem, the Windows® 2000 operating system, the Unix operating system,the Linux operating system, the Xenix operating system, the IBM AIX®operating system, the Hewlett-Packard UX® operating system, the NovellNetware® operating system, the Sun Microsystems Solaris® operatingsystem, the OS/2® operating system, the BeOS® operating system, theMacintosh operating system, the Apache operating system, an OpenStep®operating system or another operating system or platform.

It is appreciated that in order to practice the method of the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing as described above is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, or any client server system thatprovides communication, for example. Such communications technologiesmay use any suitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions is used in the processing ofthe invention. The set of instructions may be in the form of a programor software. The software may be in the form of system software orapplication software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instructions or single programminglanguage be utilized in conjunction with the operation of the system andmethod of the invention. Rather, any number of different programminglanguages may be utilized as is necessary or desirable.

Also, the instructions and/or data used in the practice of the inventionmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, whichenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, a EPROM, a wire, a cable, a fiber,communications channel, a satellite transmissions or other remotetransmission, as well as any other medium or source of data that may beread by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for examine.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, voice reader,voice recognizer, dialogue screen, menu box, list, checkbox, toggleswitch, a pushbutton or any other device that allows a user to receiveinformation regarding the operation of the processing machine as itprocesses a set of instructions and/or provide the processing machinewith information. Accordingly, the user interface is any device thatprovides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

It will be readily understood by those persons skilled in the art thatthe present invention is susceptible to broad utility and application.Many embodiments and adaptations of the present invention other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and foregoing description thereof, withoutdeparting from the substance or scope of the invention.

Accordingly, while the present invention has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentinvention and is made to provide an enabling disclosure of theinvention. Accordingly, the foregoing disclosure is not intended to beconstrued or to limit the present invention or otherwise to exclude anyother such embodiments, adaptations, variations, modifications andequivalent arrangements.

Electronic Invoicing

Using the system of the present invention, sellers are able to exportinvoice data from their account receivables, billing or other invoicingsystem and upload that data to be electronically sent through the systemnetwork. The system of the present invention provides an automaticconfiguration feature which walks sellers through the process of mappingan exported invoice file format to the buyer's invoicing fields in orderto pre-certify their file format for production electronic invoicing.The system will ask the seller for specific invoice field values as atest invoice which the seller exports and uploads into the system. Thesystem then automatically maps those values to the buyer's requiredinvoice fields.

The automated mapping feature allows a user to convert paper invoicesinto electronic invoices. The system receives a scanned image of a paperinvoice and uses the mapping feature to match the data from the imagewith the mapped field values, and insert the data into an electronicinvoice form. The electronic invoice can then be sent directly to thebuyer for reconciliation.

Another advantage of the system of the present invention is that isallows for bulk-upload of invoices. Typically bulk invoicing requires aseparate mapping network at the seller's end, which can be veryexpensive and time consuming. The system of the present inventionprovides all mapping for the seller to allow for easy upload of multipleinvoices.

Referring now to FIG. 1, a seller first sets up an account with thesystem 101. The seller then downloads instructions and a test invoicefrom the system for Buyer 1102. The seller will then enter the testinvoice into their own accounts receivable system for completion of theappropriate data for the field values 103, exports the completed testinvoice as a CSV file and uploads the CSV file to the invoicing system104. In preferred embodiments, the invoice field values contain a rangeof tolerances that are acceptable to the seller. The system isprogrammed to recognize the reference transaction and the file typeusing recognition logic 105, and creates a mapping field to map theinvoice field values using mapping logic 106. The system validates thedata entered into by the seller using validation logic 107. If there isan error, the system will notify the seller using notification logic108. The seller will need to reenter the information into the system,beginning at step 103. In certain embodiments, the system also presentsthe seller with a manual mapping tool to use for any information whichthe seller may need to input manually (not shown). If the test invoicehas been uploaded accurately, the system will record the status of theinvoice for the applicable buyer as “ready” using recordation logic 109.In certain embodiments, Buyer1 will receive a test transaction from thesystem to further validate the accuracy of the test invoice usingtesting logic 110. Seller will receive notification from the buyer,either directly or through the system, informing the seller that thetest transaction has been completed 110. In certain embodiments, theseller creates a credit transaction to further test the test invoice111.

Once the test invoice is completed and validated, seller can now beginto upload invoices into the system to convert paper invoices intoelectronic invoices. Single invoices can be uploaded, or invoices can bebulk-uploaded into the system. Referring now to FIG. 2, preferably, ifthe buyer is funding the account, then the seller simply faxes or mailsthe paper invoice to a number or mailbox which is specified for thatparticular buyer 201. The system then identifies the appropriate buyerfields in the invoice using identification logic 202, the invoice isscanned into the system 203, and then proceeds to invoice entry usingrouting logic, shown in FIG. 3 a. If the seller is funding the account,preferably the seller prepares a coversheet containing buyeridentification 204. In certain embodiments, the cover sheet can bepre-printed with buyer information. The seller then faxes or mails theinvoice with the coversheet to a single number or mailbox 205. Thesystem scans in the coversheet and the invoice 206 and then checks thedatabases to determine if the buyer exists in the system usingverification logic 207. If the buyer identification is not present inthe system, the invoice proceeds to the rejection process using routinglogic, shown in FIG. 3 b. If the buyer identification is present in thesystem, the system then determines if the buyer is a public or privatecompany using determination logic 208. Preferably, private companieswill have credit cards on file to charge settle the transaction 209. Ifthe initial card transaction fails, the invoice proceeds to therejection process using routing logic, shown in FIG. 3 b. If the initialcard transaction passes, the system enters the invoice into the system211 using routing logic, as shown in FIG. 3 a. Similarly for publiccompanies, the system checks to verify the public company is in goodstanding using verification logic 210. If the public company is in goodstanding, the invoice gets entered into the system 211 using routinglogic, as shown in FIG. 3 a. If the public company is not in goodstanding, the invoice proceeds to rejection using routing logic, asshown in FIG. 3 b.

Referring now to FIG. 3 a, if the invoice is proceeding to entry, thesystem verifies if there is an accompanying purchase order (PO) enteredinto the system using verification logic 301. If there is anaccompanying PO, the system will input the invoice line detail into theinvoice using matching logic 302, based on the test invoice previouslyentered. If the invoice field values contain a range of tolerances, thesystem will verify the data contained in the paper invoices fall withinthe range of tolerances (not shown). If the data does not fall withinthe range of tolerances, the system will notify the seller accordingly(not shown). If there is not an accompanying PO, the system will enter asummary of the invoice 303. The system will then automatically load allfiles to the disburser using loading logic 304, completing the entryprocess. In preferred embodiments, buyers with multiple invoices will beadded collectively and billed monthly 305.

Referring now to FIG. 3 b, if the invoice is rejected, the system entersthe reasons for rejection into the system using entry logic 306 andcreates a notification 307 using notification logic which is then sentto the seller 308. Rejection notification may be sent, e.g., by e-mail,fax, or mail.

Non-Member Invoice Webforms

In certain embodiments, the present invention also allows buyers toprovide select sellers who are not members of the network with theability to submit invoices through a publicly available interface. Suchan embodiment allows non-member sellers to submit invoice information tobuyers through standardized web forms without the need to login or signup for a network account.

In preferred embodiments, the standard webform has entry fieldsidentified by the buyer and seller, a security control tool, andstandard terms and conditions for electronic invoicing.

The non-member seller will be provided with information to find theappropriate form to use with the buyer. In order to facilitate theprocess, the system will store each buyer's unique identification. Thenon-member seller will then be able to use the buyer's identification toaccess the appropriate invoice.

Upon initial use, the buyer will verify buyer identificationinformation, such as a unique number or an e-mail address, to ensurethat sellers are receiving accurate information. Non-member sellers willalso have identifying information stored on the system, such as, forexample, a unique number or an e-mail address. The non-member selleridentification will be used to link to the buyer's correct vendor,remittance site, and set, if there are multiple ERP's on record.

The buyer will provide all necessary information to the non-memberseller, preferably in an e-mail, for logging onto the system andaccessing the buyer invoice. Necessary webform information includes,e.g., a link to the interface, such as a URL, the buyer's identifyinginformation (e.g., unique buyer organization system identification,buyer's requester e-mail address, etc.) and the seller's identifyinginformation (e.g., seller's e-mail address, seller's remittance address,captcha code verification, etc.). Non-member seller invoice entry istypically initiated with a message from the buyer providing thenon-member seller with the information the non-member seller will needto create an invoice. Once the non-member seller navigates to the publicinterface, an invoice webform will be presented. The non-member sellerwill be directed to complete the form appropriately. After completion ofthe webform, the system will verify if the identifying information forboth the buyer and the seller is valid.

Once all information is validated, the buyer will then need to approvethe invoice. The buyer will receive notification from the system that aninvoice has been submitted by a seller. Invoices will be stored in thesystem and accessible to the buyer. The buyer can search for invoicesthough the system, based on their unique permissions. The buyer can thenadd additional information if needed, save for later submission, approveor reject the invoice.

Referring now to FIG. 4, the buyer will first enter the non-memberseller identification into the system 401. When the buyer has enteredmultiple non-member sellers into the system, the buyer has the option toselect the specific non-member seller who will receive the webforminformation 402. A notification is then sent to the seller regardingtheir entry into the system using notification logic 403. Thenotification will contain the necessary information required to accessthe buyer's webform, which includes a URL, hyperlink or web address tothe public interface. Either the system or the buyer can send thenotification to the non-member. The non-member seller will then accessthe interface to obtain the webform 404. The non-member seller entersthe requested identifying information into the system 405, along withinvoice data directly into the webform 406. For security purposes, theinterface may require the seller to provide security information, suchas, e.g., a challenge key, numerical identification number (e.g.,non-sequential 6-11 digit number), e-mail address of buyer or seller,captcha image, etc. 407. The system may also require that the selleraccept the interface terms and conditions 407. Once completed, theseller then sends the invoice request into the system 408. The systemdetermines if the requested identifying information is valid usingvalidation logic 409. If valid, the invoice request is converted to aninvoice and proceeds to invoice exception processing using routing logic410. If the credentials cannot be validated by the system, the systemwill notify the seller of the rejection using notification logic 413.Once validated, the system then verifies that all information insertedinto the webform is in proper format using verification logic 410. Ifvalidated, the invoice then moves on for buyer approval using routinglogic 411. If the invoice information is not validated, the seller willreceive notification from the system of the same using notificationlogic 413.

Additional System Capabilities

In addition to electronic invoice submission, the system of the presentinvention can be used in conjunction with existing ERP and legacyapplications to create a central seller management system that improvesand simplifies seller profile data. In such embodiments, the systemadditionally provides advanced shipment notification, invoice paymentprocesses, rich remittance data with payments, real time validation andmatching, online status tracking, collaborative online disputeresolution, and robust security.

The foregoing description of various embodiments of the invention havebeen presented for purposes of illustration and description. It is notintended to limit the invention to the precise forms described.

What is claimed:
 1. A computer-implemented method for generating batchinvoices comprising: receiving, at a programmed computer, a set ofinvoice field values provided by a user; automatically mapping, usingthe programmed computer; the invoice field values provided by the userto create mapped data fields; receiving, using the programmed computer,a batch of production invoices comprising individual production invoicesof the user, wherein the individual production invoices compriseidentification of a buyer; verifying, using the programmed computer, thebuyer identification; determining, using the programmed computer,whether the buyer is a public company or a private company; verifying,using the programmed computer, the public company is in good standingupon determining that the buyer is a public company, wherein the batchof production invoices is permitted to be processed upon determining thepublic company is in good standing; verifying, using the programmedcomputer, the private company has a credit card on file upon determiningthat the buyer is a private company, wherein the batch of productioninvoices is permitted to be processed upon determining the privatecompany has a credit card on file; and applying, using the programmedcomputer, the mapped data fields to the batch of production invoices tocreate a batch of electronic invoices.
 2. The computer-implementedmethod of claim 1, further comprising providing a manual mapping tool.3. The computer-implemented method of claim 2, wherein the mapping toolis used by the user to manually map at least a portion of the invoicefield values.
 4. The computer-implemented method of claim 1, furthercomprising displaying the mapped data on a computer screen of the user.5. The computer-implemented method of claim 1, further comprisingproviding the status of the batch of production invoices to the user. 6.The computer-implemented method of claim 1, wherein at least a portionof the invoice field values comprise a range of tolerances for theinvoice field values.
 7. The computer-implemented method of claim 6,further comprising determining whether data in the batch of productioninvoices falls within the range of tolerances.
 8. Thecomputer-implemented method of claim 7, further comprising notifying theseller when data in the batch of production invoices does not fallwithin the range of tolerances.
 9. The computer-implemented method ofclaim 1, further comprising providing the batch of completed invoices toa second user.
 10. A system for generating batch invoices comprising: aprocessor; a memory; and an application stored in the memory of thesystem and executable by the processor, wherein the applicationfunctions to: receive a set of invoice field values provided by a user;automatically map the invoice field values provided by the user tocreate mapped data fields; receive a batch of production invoicescomprising individual production invoices from the user, wherein theindividual production invoices comprise identification of a buyer;verify the buyer identification; determine whether the buyer is a publiccompany or a private company; verify the public company is in goodstanding upon determining that the buyer is a public company, whereinthe batch of production invoices is permitted to be processed upondetermining the public company is in good standing; verify the privatecompany has a credit card on file upon determining that the buyer is aprivate company, wherein the batch of production invoices is permittedto be processed upon determining the private company has a credit cardon file; and apply the mapped data fields to the batch of productioninvoices to create a batch of electronic invoices.
 11. The system ofclaim 10, wherein the application provides a manual mapping tool. 12.The system of claim 11, wherein the mapping tool is used by the user tomanually map at least a portion of the invoice field values.
 13. Thesystem of claim 10, wherein the application displays the mapped data ona computer screen of the user.
 14. The system of claim 10, wherein theapplication provides the status of the batch of production invoices tothe user.
 15. The system of claim 10, wherein at least a portion of theinvoice field values comprise a range of tolerances for the invoicefield values.
 16. The system of claim 15, wherein the applicationdetermines whether data in the batch of production invoices falls withinthe range of tolerances.
 17. The system of claim 16, wherein theapplication notifies the user when data in the batch of productioninvoices does not fall within the range of tolerances.
 18. The system ofclaim 10, wherein the application provides the batch of completedinvoices to a second user.
 19. A non-transitory computer readable mediumhaving stored thereon a plurality of instructions, the plurality ofinstructions including instructions that, when executed by a processor,cause the processor to perform the steps of a method for generatingbatch invoices, the method comprising the steps of: receiving a set ofinvoice field values provided by a user; automatically mapping theinvoice field values provided by the user to create mapped data fields;receiving a batch of production invoices comprising individualproduction invoices from the user, wherein the individual productioninvoices comprise identification of a buyer; verifying the buyeridentification; determining whether the buyer is a public company or aprivate company; verifying that the public company is in good standingupon determination that the buyer is a public company, wherein the batchof production invoices is permitted to be processed upon determining thepublic company is in good standing; verifying the private company has acredit card on file upon determination that the buyer is a privatecompany, wherein the batch of production invoices is permitted to beprocessed upon determining the private company has a credit card onfile; and applying the mapped data fields to the batch of productioninvoices to create the batch of electronic invoices.
 20. Thenon-transitory computer readable medium of claim 19, further comprisingproviding a manual mapping tool.